Skip to content

feat(ripple): add memo field to RippleSignTx for THORChain swap routing#110

Closed
BitHighlander wants to merge 1 commit into
keepkey:masterfrom
BitHighlander:up/ripple-memo
Closed

feat(ripple): add memo field to RippleSignTx for THORChain swap routing#110
BitHighlander wants to merge 1 commit into
keepkey:masterfrom
BitHighlander:up/ripple-memo

Conversation

@BitHighlander

Copy link
Copy Markdown
Collaborator

What

Adds optional string memo = 7; to RippleSignTx.

 message RippleSignTx {
     optional RipplePayment payment = 6;			// Payment transaction type
+    optional string memo = 7;					// transaction memo (e.g. THORChain swap routing memo)
 }

Why

XRP is a supported THORChain swap asset. THORChain routes swaps via a memo
string on the transaction; without a memo field the device cannot sign
XRP→THORChain swaps. This lets the host supply the routing memo for the device
to display and sign.

Wire compatibility

  • New optional field, tag 7 — additive, backward compatible.
  • Existing XRP payment signing is unchanged when memo is omitted.

Downstream

Consumed by keepkey-firmware (memo display) and python-keepkey; staged to pin
once merged.

@BitHighlander

Copy link
Copy Markdown
Collaborator Author

Consolidating into a single comprehensive device-protocol PR covering the entire firmware release (not per-field).

@BitHighlander BitHighlander deleted the up/ripple-memo branch June 30, 2026 05:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant